home *** CD-ROM | disk | FTP | other *** search
- Subject: Digestion
- Date: Tue, 14 Jun 1994 15:18:46 +1000
- From: Warwick Allison <warwick@cs.uq.oz.au>
- Precedence: bulk
-
- Michel Forget wrote:
- > I decide that I want the original back, so I press Control-H.
- > The changes are thrown away and the document is reloaded.
-
- Scrap the whole concept of an `Abandon' option. It makes more sense
- to just provide a Close option that gives `Cancel | Abandon | Save'
- options. Otherwise, Close would still be expected to provide that
- alert, and Abandon would be expected to provide `Cancel | Abandon'!!
-
-
- Evan K. Langlois:
- > Can someone please check and see if the keyboard state variable (state of
- > cntrl-alt-shifts) that is returned from evnt_multi() is valid when a
- > keyboard occurs.
-
- Not only is it valid for keyboard and mouse, it is also valid for timer
- events. Even the mouse position is valid for keyboard (and timer) events
- that occur in evnt_multi().
-
-
- Damien M. Jones:
- > Is it absolutely necessary for everyone to respond with an "I
- > agree to this" message...
-
- On a newsgroup, no. But on a mailing list, it is sometimes necessary
- to show agreement, as that helps to coagulate the general opinion of
- the group. If we only ever heard `Nay', then we'd start to think that
- stdization was impossible.
-
- > _yet_another_ file sitting in the root directory.
-
- APP-DEFS.SYS should be searched for in the root dir, then elsewhere,
- such as /system, etc. This is all just damage-control for Atari not
- thinking of such a solution in the first place. ASSIGN.SYS should
- never have existed. It cold be done with APP-DEFS.SYS. So could
- just about all other SYS and INF files that are polluting C:\
-
- > And I think .SYS is a bad extension for this file. Keep in mind that
- > this is something the _user_ will be editing. Don't scare them away!
-
- How is that different from ASSIGN.SYS? For years, the user was expected
- to edit ASSIGN.SYS, then along came some apps with Speedo to automate
- it. I suggest that APP-DEFS.SYS will take a shortcut and have app-based
- editing right from the start.
-
- > Why have a standard, if you have a key-definition file.
-
- It specifies which keys should be avoided in app-specific lines of
- the APP-DEFS.SYS file. Simple? Std is necessary.
-
- What the APP-DEFS.SYS does is make the stdization process much simpler,
- as it's not necessary to please all the people all the time. You just
- have to ensure that people can please themselves.
-
-
- Ofir:
- > I'm against an ASCII file for the user to edit. Parsing is a pain and
- > users are likely to hate it anyway. Someone will have to create an editor.
-
- I sent out the parsing code (it's trivial), so an ASCII file is fine.
- This is not to say that it should always be created by a text editor.
- I would like to see an editor for APP-DEFS.SYS that included some support
- for `installing' an APP-DEFS.SYS from a s/w package. This might be
- as simple as stripping repeats and appending the rest.
-
- Annius:
- > [Shift-FULLER for iconify] Makes sense...Should this be part of the standard?
-
- It should, since it is a shortcut. Thought about this started when a key
- shortcut for iconify was suggested. In general, I would suggest we avoid
- modified window-gadget-clicks, but this is just to provide iconification
- in older GEM versions.
-
- Damien M. Jones:
- > What I'd rather see is a method whereby programs can retrieve a set of
- > "global" keyboard shortcuts, but in the absence of such a set, can use
- > whatever the programmer feels is "best" for that particular
- > application.
-
- While this is easy for the application writer to implement, it shouldn't
- be necessary, as an application should always be provided with a start-up
- APP-DEFS.SYS file. Installation error is the only reason why such a file
- would not exist. The app could simply copy a local APP-DEFS.SYS to the
- system-wide location of APP-DEFS.SYS if not found.
-
-
- Evan K. Langlois:
- > This means all apps could use the same [APP-DEFS.SYS] file, or you could
- > make lots of separate files for each program...
-
- There should only be one APP-DEFS.SYS file [per user], as that file has
- the ability to specify application-specific as well as system-wide defaults.
- Possibly even application-type-specific, if that was standardized (we'd have
- one over X11 there). eg. wp.editress.*, wp.tempus.*; or textedit.editress.*!?
-
- > I recommend [SHORTCUT.INF] as the name
-
- Not only shortcuts can be stored. Any config attribute at all can be
- easily included. APP-DEFS.SYS or APP-CONF.SYS or APPL-DEF.SYS [Apple!!eeek!].
-
-
- Evan K. Langlois:
- > Drag-n-Drop was a move, not a copy. My docs don't mention that.
- > I think it should always be a copy.
-
- Apple got it wrong (they use move). Move is a macro for copy-then-delete,
- so the basic op should be copy. We can laugh at Apple.
-
-
- General:
-
- * I disagree with double-clicking in general, and double-keying absolutely.
-
- * Adding configuration to every app has two major failings:
- - Repeated, inconsistent code.
- - Every app must be changed to the user's preferences, rather
- than the user setting prefs, then all apps using them.
-
- * Anyone at all looked at that APP-DEFS.SYS code I posted? Would you
- prefer it in ASCII rather than a UUencoded zip file?
-
-
- --
- Warwick
- ps. Ofir, one other person doesn't digets their replies...... ?:)
-